Skip to content

Conversation

@josh-wong
Copy link
Member

Description

This PR:

  • Adds ScalarDB 3.16 docs as the latest version.
  • Moves the ScalarDB 3.15 docs to a versioned folder.

Related issues and/or PRs

  • Added docs for ScalarDB 3.16 as the latest version for English and Japanese docs.
  • Moved the docs for ScalarDB 3.15 to a versioned folder for English and Japanese docs.

Changes made

Outline the specific changes made in this pull request. Include relevant details, such as added features, bug fixes, code refactoring, or improvements.

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

  • I have updated the side navigation as necessary.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have updated the documentation to reflect the changes.
  • Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
  • My changes generate no new warnings.
  • Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

N/A

ABAC was introduced in 3.15, so we shouldn't re-introduce it here.
@josh-wong josh-wong self-assigned this Jul 10, 2025
@josh-wong josh-wong added the documentation Improvements or additions to documentation label Jul 10, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @josh-wong, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on updating the ScalarDB documentation to reflect the release of version 3.16. It involves promoting the new version's content as the latest and archiving the previous version's documentation, along with necessary configuration adjustments to the documentation platform.

Highlights

  • Documentation Promotion: The ScalarDB 3.16 documentation has been promoted to be the 'latest' and 'current' version across the English and Japanese sites.
  • Version Archiving: The previous ScalarDB 3.15 documentation has been moved into a dedicated versioned folder, ensuring historical access while keeping the main site up-to-date.
  • Release Notes Update: Detailed release notes for ScalarDB 3.16.0 have been added, highlighting numerous enhancements (e.g., IBM Db2 support, new scanner API, read-only transactions, one-phase commit optimization), improvements, and bug fixes for both Community and Enterprise editions.
  • Configuration and UI Updates: The Docusaurus configuration has been updated to reflect the new versioning, including changes to the navigation, language dropdown, and the site's announcement bar to notify users of the 3.16 release.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation for the ScalarDB 3.16 release. The changes include updating release notes, versioning the 3.15 documentation, and updating configuration files. I have identified some issues with links and a recommendation to use backticks for string literals. Addressing these points will ensure the documentation is accurate.

@josh-wong josh-wong force-pushed the prepare-version-3.16 branch from 8c59f8f to c1ec591 Compare July 10, 2025 02:51
@josh-wong josh-wong marked this pull request as ready for review July 10, 2025 03:12
@josh-wong josh-wong merged commit 3116aa5 into main Jul 10, 2025
1 check passed
@josh-wong josh-wong deleted the prepare-version-3.16 branch July 10, 2025 03:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant